Restoring a SQL Server vault to another server

A Meridian vault can be moved to another computer (for example, as a server upgrade) by restoring a backup of the vault made on the original server and by modifying the vault configuration file.

Warning    To move (by restoring from backup) a vault from a pre-Windows Server 2008 computer (including Windows XP, Windows Server 2000, or Windows Server 2003) to a post-Windows Server 2008 (including Windows Vista) or later computer, see Changing operating system versions.

Notes

To restore a SQL Server vault on another server:

  1. On the original server, create a backup of the vault as described in Preparing for backups.
  2. Edit the resulting DataStore.ini file in any text editor and change or add the following settings. For descriptions of each setting, see HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Installed DataStores\<vaultname>\CompoundItemService and HKEY_LOCAL_MACHINE\Software\Cyco\AutoManager Meridian\CurrentVersion\Installed DataStores\<vaultname>\StreamService.
  3. Copy the modified DataStore.ini file and the contents of the Backup folder from the old server to the new server location \\<ServerShare>\BC-Meridian Vaults\<Vault>\Backup.
  4. Copy the vault streams folders from the old server to the new server location <ServerShare>\BC-Meridian Vaults\<Vault>.
  5. On the new server, restore the vault using the modified DataStore.ini file as described in Restoring backups.

Related concepts

Integrating Meridian with SQL Server

Understanding how Meridian works with SQL Server

Understanding SQLIO

Understanding vault cache memory

Understanding SQL Server vault backups

Related tasks

Integrating with a separate SQL Server computer

Configuring the Windows account used by Meridian

Creating a SQL Server account for use by Meridian

Configuring the SQL Server account used by Meridian

Migrating a Hypertrieve vault to SQL Server

Moving a SQL Server vault to a different folder

Monitoring SQL Server vault performance

Minimizing SQL Server log file size